Skip to content

chore: upgrade eve to 1.0.0-rc.1 - #13

Open
cmpadden wants to merge 4 commits into
browser-use:mainfrom
cmpadden:chore/eve-1.0.0-rc
Open

cmpadden wants to merge 4 commits into
browser-use:mainfrom
cmpadden:chore/eve-1.0.0-rc

Conversation

@cmpadden

@cmpadden cmpadden commented Oct 30, 2026 •

Copy link
Copy Markdown

🔗 Linked issue

📚 Description

Upgrades the Browser Agent gallery template to eve 1.0.0-rc.1, including the v27 React session-store and interaction/tool-part migrations. Updates the eve-required @vercel/connect and AI SDK peer integrations and regenerates the pnpm lockfile.

Refreshes the target to eve@1.0.0-rc.1 and its required @vercel/connect@2.7.0 integration; the committed pnpm lockfile was regenerated.

Gallery: https://vercel.com/templates/eve/eve-browser-agent

Validation run for rc.1:

  • pnpm install --no-frozen-lockfile — passed.
  • pnpm typecheck — passed.
  • pnpm peers check still reports the unsupported Browser Use/eve peer combination.
  • pnpm exec eve build --skip-sandbox-prewarm — blocked by the unchanged old Browser Use sandbox distribution.

Blocker: latest @browser_use/eve@0.0.4 still requires eve below 1 and fails the 1.0 sandbox contract. A compatible upstream extension is required before this PR can merge. The existing npm lockfile also remains blocked on resolving that incompatible peer; it was not bypassed or falsely regenerated.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.
  • npm run typecheck passes locally.

Summary by cubic

Upgrades the Browser Agent gallery template to eve 1.0.0-rc.1 with the required @vercel/connect 2.7.0 and AI SDK 7.0.158 peers, and regenerates the pnpm lockfile.

  • Migrates message parts from dynamic-tool to tool, adds interaction parts for approvals, free-text answers, and sign-in prompts, and switches to the v27 session-store send/cancel/respond API.
  • Updates tool status rendering for the new part states and excludes eve@1.0.0-rc.1 and @vercel/connect@2.7.0 from the pnpm release-age policy.
  • Documents in the README that the migration intentionally keeps the @browser_use/eve extension and its peer validation.

Blocker: the pinned @browser_use/eve (0.0.4) declares eve <1, and no compatible release exists, so a clean npm install stays blocked until Browser Use publishes an Eve 1-compatible extension.

Written for commit 869a19d. Summary will update on new commits.

View guided diff

Signed-off-by: Colton Padden <colton.padden@vercel.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 6 files

Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.

View guided diff | Re-trigger cubic

Comment thread package.json Resolved
Comment thread app/_components/agent-message.tsx Resolved
Comment thread app/_components/agent-message.tsx Resolved
Comment thread package.json Resolved
Comment thread app/_components/agent-message.tsx Resolved
Comment thread app/_components/agent-chat.tsx Resolved
Signed-off-by: Colton Padden <colton.padden@vercel.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 3 files (changes from recent commits).

Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.

View guided diff | Re-trigger cubic

Comment thread app/_components/agent-chat.tsx Resolved
Comment thread README.md Resolved
Signed-off-by: Colton Padden <colton.padden@vercel.com>
Signed-off-by: Colton Padden <colton.padden@vercel.com>
@cmpadden cmpadden changed the title chore: upgrade eve to 1.0.0-rc.0 chore: upgrade eve to 1.0.0-rc.1 Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant